Internet Info 1994 March

home *** CD-ROM | disk | FTP | other *** search

/ Internet Info 1994 March / Internet Info CD-ROM (Walnut Creek) (March 1994).iso / answers / comp / ibm-rt-faq / aix-v2 / software / part1 < prev next >

Wrap

Internet Message Format | 1994-04-04 | 59.6 KB

Path: bloom-beacon.mit.edu!hookup!news.moneng.mei.com!howland.reston.ans.net!cs.utexas.edu!swrinde!news.uh.edu!lobster!antimatr!faq-rt From: faq-rt@antimatr.hou.tx.us (Mark Whetzel) Newsgroups: comp.sys.ibm.pc.rt,comp.unix.aix,comp.answers,news.answers Subject: COMP.SYS.IBM.PC.RT: AIX V2 FAQ - Software questions, Part 1 of 3 Summary: This posting contains Frequently Asked Questions (and their answers) on software issues when using AIX V2.2.x on IBM RT (615x) computers. Plus general information, hints and tips. Keywords: IBM RT PC software FAQ 6150 6151 6152 AIX VRM AOS MACH PICK Message-ID: <ibmrt_aixv2s1_765425273@antimatr.hou.tx.us> Date: 4 Apr 94 02:08:25 GMT Expires: 17 May 94 02:07:53 GMT References: <ibmrt_aixv2ix_765425273@antimatr.hou.tx.us> Sender: markw@antimatr.hou.tx.us Reply-To: aix-rt@antimatr.hou.tx.us Followup-To: comp.sys.ibm.pc.rt Lines: 1445 Approved: news-answers-request@MIT.Edu Supersedes: <unknown> Xref: bloom-beacon.mit.edu comp.sys.ibm.pc.rt:1495 comp.unix.aix:23020 comp.answers:4430 news.answers:17302 Archive-name: ibm-rt-faq/aix-v2/software/part1 Last-modified: Fri Mar 25 03:26:52 CST 1994 Version: 1.1 Frequently Asked Questions for: AIX V2.2.1 on IBM RT systems. System Software topics for AIX/RT. Part 1 of 3 parts. The AIX V2 FAQ currently consists of EIGHT parts in 5 topic areas: AIX V2 FAQ Index and acknowledgements AIX V2 OS Specific hardware issues - in one part (currently). AIX V2 Software questions - in three parts. (This FAQ) AIX V2 Problem Questions and answers - two parts. AIX V2 Porting software notes See the AIX V2 FAQ index posting for a complete index of the AIX FAQ postings. This FAQ covers system software usage and questions concerning using AIX V2 on an IBM RT system. ================================================================================ 2.0 Software questions. S.1 - What is AIX? The operating system is called AIX, for Advanced Interactive Executive, and is based on the UNIX system V operating system. During AIX development, enhancements were added by IBM and by INTERACTIVE System Corporation under contract to IBM. These enhancements were made to improve the AIX Operating System's functions and ease-of-use, merge in selected facilities of BSD 4.2, (and later some BSD 4.3), and to take advantage of the RT PC technology. The enhancements consist of functions exclusive to IBM and the RT PC, along with functions from several versions of UNIX, including BSD and Interactive Systems. For example, the AIX Operating System includes a C compiler, Asynchronous Terminal Emulation, and the INed full-screen editor. AIX for the IBM RT 6150 and 6151 machines has been discontinued by IBM. Formal support of AIX V2 by IBM ended on June 1, 1991. Sales of 6150 and 6151 machines also ended on that date, replaced by the IBM Risc/System 6000 line of workstations. Features of the AIX/RT operating system: * Editors: vi, ed, INed. * Shells: - Enhanced Bourne shell - C shell - DOS services, a shell allowing users to use IBM PC DOS-like commands accessing both AIX and DOS files. * Library routines: - Expanded curses library. - Expanded terminfo library. - Routines for DOS services. - Shared libraries, allowing run-time linking of user-written routines. * Kernel: - Extended inter-process communication (semaphores, messages, shared memory) - Enhanced signals. - Multiple concurrent group access. - Filesystem enhancements such as file syncronization and trunication. - Enhanced process management to explot the 40-bit address space. - Page fault handling on demand. - Fork enhancement. - Memory mapped files. * International Character Support. * Graphics - Grapics Development toolkit. - Advanced Display Graphics support library. * User interface - Enhanced installation, device configuration, and system customization. - Usability Services, a point-and-select interface to AIX commands. * Optimizing C Compiler. * Other functional enhancements: - Generalized queueing system for job and print queue management. - File system extensions for minidisk devices. - I/O managment extensions including: - Dynamiclly configured device drivers. - Support for virtual terminals and SNA sessions. - Generic device independent device drivers. - Multiple virtual terminal support on the native consoles. - Support for logical disks (minidisks) - Error log collection and analysis, trace recording and dump facilities. Portions of the above were quoted from IBM RT Personal Computer General Information book, Second Edition (July 1987) GC23-0783-1. ------------------------------ S.2 - What is VRM? Unlike many operating systems derived from UNIX, AIX V2 is divided into two layers: the kernel, and the Virtual Resource Manager (VRM). The kernel is the core of the operating system; it implements the AIX file system, user process management, system call interface, and other UNIX-like features. The VRM provides a virtual machine environment for the kernel, shielding it from specific hardware characteristics and from changes or additions to the hardware. The VRM also allows more than one operating system (and their applications) to execute. To a guest operating system, the VRM is percieved as hardware. The interface between the VRM and the AIX kernel is known as the Virtual Machine Interface (VMI). VRM is conceptually similar to the control program for the IBM Virtual Machine/System Product on machines with an IBM System/370 architecture, except that while the VM/370 control program emulates the System/370 hardware architecture, the VRM emulates a hypothetical machine with powerful features that are not usually implemented in hardware. VRM however, lacks major features of an operating system, such as a file system and a user interface; these services are provided by the AIX kernel. The VRM processes, device drivers and runtime routines extend and control hardware functions for guest operating systems. - Portions of the above were quoted from IBM RT Personal Computer General Information book, Second Edition (July 1987) GC23-0783-1. VRM it seems, was not written in standard C. Some books seem to indicate that it is written in PL8. Possibly a derivation of PL/1 or an IBM internal language called PL/S. Portions of the MVS operating system are written in PL/S. I don't have good conformation of the exact details of VRM, nor good documentation of some of the interfaces, other than in the VRM Device Support and VRM Programming reference manuals. [Anybody know more details of VRM? How it came about? Design? - MW] ------------------------------ S.3 - The RT will not boot from floppy, but does boot from the internal hard disks, why? Also VRM unique keyboard sequences. As shipped by IBM, the only diskettes that are bootable are: - Diagnostic diskette #1 - VRM Install diskette #1 - Any VRM backup diskettes made with the 'cvid' command, has diskette #1 as a bootable floppy. The AIX Install/maintence diskette while it appears bootable is in fact not directly bootable. VRM is the OS that actually owns the machine during normal operation when using AIX, and when 'booting' the AIX Install/Maintence diskette, you are still booting VRM from the internal hard disks. VRM examines the floppy drive to determine if a runable guest system image and boot record is on the diskette in the drive. The AIX Install/maintence diskette has very special version of the AIX kernel on it, and THAT is being loaded from the floppy. This special AIX diskette includes a kernel built that requires no external hard disks (except that containing VRM), and places all of it's filesystems in RAM with a special device driver in this kernel on diskette that allows ram simulation of disk filesystems. Sometimes, either by accident, or overt action, the Non-Volitale Random Access Memory (NVRAM) has been altered to not allow the floppy drive to be used as a boot device. The NVRAM, in the RT planar, maintains, along with the time of day clock setting, various system parameters, AND a list of last and currently selected boot devices. This list may be updated at any time by some special key sequences entered ONLY from the native keyboard. The VRM software that controls the RT hardware silently accepts these special keystroke patterns and may update NVRAM or alter system operation. The NVRAM contents and clock are maintained while the system is powered off by the battery attached to the operator key panel. By referencing the chart below, you can reset the available boot device list from one of the hard drives back to the floppy drive. These keyboard sequences are directly captured as long as VRM running. You do NOT have to be logged in to AIX to change the settings. VRM will silently update the NVRAM as specified by the chart below. Key-Sequence Function -------------------------------------------------------------------- Alt-Action Change active display screen to next virtual terminal (if any). cntl-Action Change active display to command virtual terminal (if defined). Shift-Action Change active display screen to previous virtual terminal (if any). Cntl-Alt-a Select diskette 0 as alternate IPL device. Cntl-Alt-b Select diskette 1 as alternate IPL device. Cntl-Alt-c Select fixed disk 0 as alternate IPL device. Cntl-Alt-d Select fixed disk 1 as alternate IPL device. Cntl-Alt-e Select fixed disk 2 as alternate IPL device. Cntl-Alt-Delete Restart the co-processor. Cntl-Alt-Action Exit the co-processor. Cntl-Alt-Home Restart a virtual machine Cntl-Alt-End Dump first virtual machine data. Cntl-Alt-NumPad 4 Activate the VRM debugger. Cntl-Alt-NumPad 7 Dump all of memory to diskette. Cntl-Alt-NumPad 8 Dump VRM data to diskette. Cntl-Alt-NumPad 6 Hard IPL the entire system. Cntl-Alt-Pause Soft IPL the entire system. ==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**== Submitter: James Moody <moody@austin.ibm.com> Date: 13 Mar 90 17:59:30 GMT Your machine is experiecing the "can't boot from diskette" bug. The first thing to try is this: Boot the machine. Hit the key sequence ctl-alt-a (all 3 keys at once). [ BTW.. this is the LEFT alt key - MW ] Shutdown and try booting from diskette. If that doesn't work, here is the failsafe approach. Boot the machine. Hit ctl-alt-numpad4 (only works if you have some display connected to the RT that is NOT the megapel). [ VRM debugger wont work on the megapel -MW ] You are now in the VRM debugger. At the prompt, do the following: >al F0008828 F0 [enter] >g [enter] You should be back in AIX now. Shutdown and reboot from diskette. If that fails (because I said something wrong here or you don't understand what I'm talking about), power off the machine and take of the front cover. Disconnect the battery back. Leave disconnected for 5 minutes or so and then reconnect. I think this is messy but it also works. [ Note: You will also have to reset the TOD clock. It will now be January 1, 1970 and on Eastern Standard time. I recommend you attempt first booting the VRM disk and use the menu items to correct the system clock before doing a normal boot of the installed AIX. - MW ] ==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**== Submitter: Nick Simicich Date: 13 Mar 90 02:09:19 GMT Power off the system, open the covers, and disconnect the battery. Let it stay disconnected for about 15 minutes with the power off. Reconnect the battery and power up the machine. It should boot from the floppy. Replacing the motherboard works, too. :-) While you're in the system, make sure that the floppy drive is connected to the controller, and that all of the connections are good. Wiggle them a bit. The RT thinks you've told it not to boot from the floppy with a keyboard sequence. Or, the floppy is broken. If the battery trick doesn't work, call your CE.) [ See the above note about the clock! - MW ] ==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**==**== ------------------------------ S.4 What operating systems are available for the RT? At the time of this posting, the following operating systems have been available for the RT processor. Availablility of these systems is unknown and unfortunately problematic. [ This section needs LOTS of work! - MW ] AIX V2 - Advanced Interactive Executive Vendor: International Business Machines Systems: IBM PC RT 6150 and 6151 Announced: Jan 1, 1986 (AIX V1.0) Available: Not generally, discontinued on June 1, 1991. Last Version: V2.2.1 Update level 1779 (opsys). Distribution: Binary format only, on installp disks. See section S.5 below. Information source: IBM announcement letters 286-004, 286-011 and 286-259 Note: Other versions of AIX exist for other platforms: AIX V1.3 - IBM PS/2 and compatible 80386 processors. AIX/ESA - IBM 3090 mainframes AIX V3.2 - IBM Risc/System 6000 processors. AOS - Academic Operating System Vendor: IBM Available: Not generally. Originally from IBM, but most academic instutions that have RT systems and Berkley source liscenses were able to get the full source. Last Version: AOS43 Dec88 ? Distribution: Source Information: IBM Announcement letter xxx-xxx, RPQ P83008 Program Number 5799-WZQ and usenet news information. BSD/RENO - ? Vendor: Berkley? Available: Unknown. This version is a combination of the AOS drivers and low level support routines, with the RENO distribution of BSD. Never made generally available. Found at academic instutions that have access to both AOS and RENO sources. Version: Reno? Distribution: Source? Information source: Netnews discussions. MACH - ? Vendor: Mt. Xinu ? Available: ? Version: msd 2.6 ? Distribution: ? Information source: Gleaned from Netnews posting May 21, 1991 PICK - (Named after author Dick Pick, of PICK Systems, Inc.) Licensee: Seattle OS, Inc., PICK Systems, Inc. Major shareholder. Systems: IBM Series/1 and IBM PC RT Completed: 1982 and 1987, respectively Processor: IBM series/1 and PC RT Available: Unknown Version: ? Distribution: Unknown, Binary system images? Information source: Exploring the PICK Operating System By Jonathan E. Sisk and Steve VanArsdale Hayden Books, Second Edition 1989 ISBN 0-672-48412-9 Note: PICK is available for a variety of processor hardware and platforms including, but not limited to: IBM PC/XT/AT/RT/Series-1 and IBM 4331/4361/303x/9370 (PICK/370), Intel 8086/80286/80385, Motorola MC68000/68020 (several vendors), Zilog Z8000 (ADDS Mentor), HP 3000, Microdata, Nixdorf 8890 VM. ------------------------------ S.5 Where can I get a copy of AIX for the RT? At this time, IBM no longer directly sells AIX V2. However, some IBM remarketers MAY still have original distribution sets still in inventory. (doubtful!) If you aquire an RT system, inquire about the software and books for the system. This is the only way you can currently get a liscensed copy of AIX, that I know of. Most liscensed software that IBM distributed for the RT is no longer carried by IBM. Some OEM vendors of software may still stock and sell their products that were made for the RT, but there is no list of available software that I am aware of. [ I'm going to maintain a seperate section for this! See section S.21 for OEM software. - MW ] ------------------------------ S.6 Where are the 'man' pages? IBM never supplied the 'man' command and the source for the man pages directly WITH the AIX distribution. They WERE available as a seperate PRPQ (Program Request Price Quote) software product, for purchase for a small fee mostly covering the distribution and media. The set of nroff files on two hi-density diskettes, covered most of the base commands, some system files and common special files. Sadly missing were the TCP/IP command set and information dealing with quite a few of the TCP and NFS daemons. RPQ: P91026 Program number: 5799-DAQ AIX/RT on line pubs ------------------------------ S.7 Contents of the AIX V2.2.1 distribution diskettes. Shown in this list is the number of disks comprising a full distrubution set of AIX V2.2.1. In parenthesis is the product abbreviation directory name, as seen in the /usr/lpp file tree. A few example commands and files are listed, plus a comment by myself (indicated by '>') on files and programs that seem badly placed in the distribution, or missing. There are 36 total 1.2Mb format diskettes shipped for AIX 2.2.1. # column indicates number of disks in that option group. # Title and contents - ------------------------------- 2 VRM install/utility disks * VRM install program, utility programs for formatting disks, and other special functions. 1 Installation/Maintenance * AIX Mini-kernel, install facilities, standalone backup programs, minidisk utilities, and more. 8 Base System Program (opsys) * base system files, including: - shells: sh, csh, tsh, Rsh. [ tsh = trusted bourne shell ] - C compiler, cpp, ld, make, ar, nm. - cpio, backup, restore. - initial /usr, /etc, /bin, /dev population. - awk, sed. - dosdir, dosread, doswrite, dosdel. 6 Extended Services Program (osplus) * Administrative support (admn) - tar, prof, tic, terminfo support, ect.. > badly placed: tar, tic, chroot, proto, prof, and the /usr/lib/terminfo/* files. (These should have been in the base set, IMHO.) * DOS services (doss) - special commands to emulate a dos envrionment from the unix command line. With the command 'dos', a special version of format, dir, mkdir, ect.. - dos to unix conversion utilities. convert, filetype, ect.. * Extended Programming Support (extp) - adb, cflow, cxref, dbx, dump, lex, yacc, ect.. > badly placed: banner, bc, cal, calendar, dc, tput, tail. * Source Code Control System (sccs) - sccs support functions. > missing the 'sccs' command shell. * Text processing/typesetting functions. (text) - nroff, troff, spell * UUCP support (bnuu) - uucp, uucico, cu, ct, ect.. * vi editor (vied) - vi, ctags, edit, expreserve, exrecover. * Games (game) - usual character based simple games, including 'fortune'. * Sendmail (send) - sendmail binary, mailstats, ect.. > Based on sendmail V5.?? (pre-1988 version) * MH Message Handler (mhmh) - MH mail handling system and commands. > version ??.?? of MH. 3 Multi-User Services Program (multiple) * Accounting Support (act) - commands and scripts for system process accounting. * System Activity recording (sar) - sar, sag > badly placed: timex. * Inter-Workstation Commands (iwc) - confer, id, mesg. * Terminal Support (trm) - commands used with some special ascii graphics displays like Tektronix 4014 terminals. - tprint, graph, greek, tplot, tc, hp. - support libraries libplot.a, libprint.a lib4014.a, ect.. * Advanced Display Graphics Support (gsl) - Graphics routines for progamming the various HFT displays on the RT, including the 6153, 6154, 6155 and megapel. - Required prereq for installing IBM's X11 product. * Graphics Device Drivers (vdi????) - device drivers for IBM RT professional Graphics Series LPP also useful for Graphics Support Library subroutines. - vdi drivers for IBM devices: 3812, 4201, 5152, 5182, 6180, 7371, 7372, 7375, ega, and vdimeta-file format. * Graphics and Statistics commands (graf) - commands used with some special ascii graphics displays like Tektronix 4014 terminals. - The /usr/bin/graf directory including, hardcopy, ceil, pie, plot, qsort, rand, erase, ect.. * HFT Examples Programs (hft) - /usr/lib/samples/hft - /usr/lib/vtm fonts for hft displays. 2 Virtual Resource Manager Device Driver (vtmdd) - Seperate components of these diskettes are installable by group of related drivers, or by individual driver. Listed below by group, with selections in that group: * RT 3278/79 Emulation Adapter - 3278/79 DFT VRM Device Driver (dft) - 3270 AIX Device Driver (3270dd) * RT baseband Adapter - Baseband VRM Device Driver [Ethernet] (enet) - Standard Baseband Data Link Control [DLC] (ethllc) - Block I/O AIX Device Driver (biodd) * RT Multiprotocol Adapter - MPDP VRM Device Driver plus microcode (mpdp) - SDLC DLC (sdlcllc) - 3270 AIX Device Driver (3270dd) * RT SCSI Adapter - SCSI VRM Device Driver (scsi) * RT Token-Ring Adapter - Token-Ring VRM Device Driver (token) - Token-Ring Diagnostics (trd) - Token-Ring DLC (trllc) - Block I/O AIX Device Driver (biodd) Note: Installable only from the individual device driver menu - IEEE Baseband DLC: 802.2 DLC with 802.3 medium access control protocol procedures (eth3llc) 3 Interface Program for use with TCP/IP (tcpip) - includes arp,finger,host,ping,rexec,rlogin,telnet,tftp,rwho, whois,setclock,lprbe,talk,netstat,route,rcp,hostid,slattach. - daemons: inetd,gated,routed,ftpd,tftpd,rwhod,fingerd,lpd,named. > badly placed: hostname,portmap,rpcinfo,x25load. 1 INED program (INed) - "e" editor command, and associated control files. 1 Asyncronous Terminal Emulation Program (ate) - ate, xmodem. 1 Base PC Network Services Program (lanserv) - IBM PC original PC Network BROADBAND adapter network support. (NOT required to be installed for Ethernet adapter use) 2 Usability Services Program (panels) - the /usr/lib/screen directory tree of panels. > badly placed: shmsystem - the shared memory segment manager! actmngr - hft activity manager - invokes a bourne shell. 3 Systems Network Architecture Services (snaserv) - SNA protocol support, LU services VRM driver. - multi-protocol adapter SNA support. 1 DOS Server program (pci) - support of the ADDU liscensed program product, extending disk and terminal support to PC users. > badly placed: aix2dos, dos2aix NL to CR-NL and CR-NL to NL text conversion utilities! 2 Update - Initial update fixes to distributed AIX 2.2.1. - MUST be installed after ALL optional AIX sections have been installed and BEFORE *ANY* other updates. ------------------------------ S.8 - Maintence? What updates are available for AIX? IBM offical support of AIX V2.2.1 ended on June 1, 1991. They however always have had service available on a fee and time basis. Some academic instutions still have IBM service contracts in effect, and some support may be available via the SE in charge of the account. After maintaining the AIX/RT systems for many years for the place where I work, and doing a little cross referencing and homework I have managaged to put together a comprehensive list of the maintance diskette history of AIX/RT for the V2.2.1 versions of AIX. Some parts of AIX history is unclear, especially in its first few updates that were issued. Support by IBMs level1 support center was VERY spotty at first, especially as IBM was firming up its support policies for AIX. Update disks were issued in two major catagories. The 17## series disks were generated by the support structure of IBM and were only sent out to customers calling in with specific problem areas needing immediate problem relief. The 17## updates were supposed to be not completely regression tested aginst all products. The 27## updates were supposed to be completely tested. Later in the AIX/RT product lifetime, the 17## disk became the ONLY update disks issued. Updates, even when offical were never automatically shipped to customers. Only if they called with a problem were any updates sent out. The earliler version of AIX V2 (2.1.x) used 15## and 16## numbered series update disks. Unfortunately, different product development groups within IBM did not coordinate the update numbers with each other, so some products have the SAME update number, but cover ONLY its product area. Other products use their own unique numbering scheme. All update disks supposedly are supposed to include ALL prior earlier maintence, completely superceeding all prior maintence. This policy however was later changed towards the end of the AIX support cycle. Disks labeled "-- NEW BASELINE --" were the final disk sets with complete prior updates on them, subsequent update disks start over on update building and require the baseline set be installed first. Each disk set is one PTF (Program Temporary Fix) and include one or more APAR (?) fixes. PTFs for AIX are always numbered U###### and AIX APARs are numbered IX######. [ Some fields are incomplete. Anybody with one of the updates listed that have some fields with question marks, I need more information and/or corrections would be welcomed. - MW ] WARNING: Personal experience with another RT user trying to update his system from the INITIAL distribution disks, shows that the update process is BROKEN.. UNLESS the initial two disk update that is supplied with the system is installed first, BEFORE any other attempted maintence. That update disk pair shows up in the opsys maintence history as 1721. Do not confuse this with the X-windows or TCP/IP updates also labeled 1721. Notes for the following chart: PE PTF in Error - one or more fixes on this disk have some problem, not necessarly critical, but with hi-impact on system operation and potentially could be critical. EFIX Disk was only sent to a customer if a problem being worked on with the support center was fixed a an intermediate level and needed immediate solution. The fix set normally was not considered a full PTF package, nor completely tested. APAR ? sup Superceedes the ptf's specified. pre Prerequesite PTF's listed need to be installed first. coreq PTF's listed must be installed at the same time. MPP Multi-Program Product - mostly the OPSYS, plus fixes to selected base and elective install parts. VRM Fixes for the Virtual Resource Manager, usually installed by IPL from diskette, and replace the entire VRM. TCPIP Diskettes are for the TCP/IP part of AIX. DOSV DOS services part of base AIX. SNA SNA services part of base AIX. Xwin Diskettes are for the AIX Windows optional product. NFS11 Diskettes are fixes for the NFS 1.1 optional product. NFS12 Diskettes are fixes for the NFS 1.2 optional product. DS Diskettes are fixes for Distributed Services optional product. WHIP11 Workstation Host Interface Program V1.1 optional product. VSP VS Pascal optional product. VSF VS Fortran optional product. VSC VS Cobol optional product. PHGS Personal GraPHIGS optional product. COPRC RT PC-AT Coprocessor Services. Within each product area the list is ordered in the sequence of release by IBM for that portion of the operating system. Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== 1706 ? Inst ? ? UNKNOWN WHAT THIS IS Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== OPSYS/MPP Component 560106103 1721 N/A MPP ??/??/88 2 Shipped with the AIX distribution set.. *MUST* be installed. 2701 N/A MPP 12/16/88 3 PartNum 002701[1-3] 1725 N/A MPP 02/09/89 2 EFIX 1733 N/A MPP 03/30/89 5 EFIX 2702 U400722 MPP 03/30/89 ? ? 1734 N/A MPP 04/05/89 5 EFIX 1735 N/A MPP 04/06/89 5 EFIX 1736 N/A MPP 04/26/89 5 EFIX 1739 N/A MPP 05/11/89 3 EFIX 1740 N/A MPP 05/11/89 7 EFIX 2703 U400727 06/22/89 10 sup(2701, U400722) 2703-D U400762 MPP 08/08/89 doc only for(U400722,U400727) 1742 ? MPP 06/15/89? ? EFIX BAD csh problems 1743 ? MPP 06/??/89? ? EFIX 1745 ? MPP 06/??/89? ? EFIX BAD tty devices problems 2704 U400751 MPP 08/02/89 12 sup(U400722,U400727,U400762) U400755 doc only for(U400751) 1749 ? MPP 08/??/89 ? EFIX BAD breaks tty xon/xoff 1750 ? MPP 08/??/89 ? EFIX 1751 U400770 08/30/89 ? BUILT BAD.. DO NOT APPLY BREAKS NFS 1757 U400857 MPP 12/01/89 9 coreq(U400849,U400843) 1758 2705 U400876 MPP 12/21/89 ? sup(U400751,U400727,U400722) pre(U400828,U400849,U400843) New INSTALL/MAINT diskette U400893 doc only dup(U400876) 2706 U400991 MPP 03/28/90 15 sup(U400876,U400751,U400727) pre(U400980,U400889) (included new Inst/Maint diskette) 1763 U?????? MPP ??/??/?? ? EFIX PE 1764 U?????? MPP ? ? EFIX PE 1765 U401041 MPP 05/04/90 ? EFIX PE 1766 U401075 MPP 06/06/90 10 EFIX PE coreq(U401043,U401039) 1769 ? MPP ? ? EFIX 1770 ? MPP ? ? EFIX BAD DO NOT APPLY! 1772 U401227 MPP 11/05/90 12 sup(U401139,U401041,U400991, U400876,U400751 U400727) pre(U401046,U401168,U401169, U401123) PE(IX08395,IX08240) 1773 U401293 MPP 01/21/91 12 BAD-BAD-BAD-BAD DO NOT INSTALL! fix set was created incorrectly breaks NFS among other things. 1773 U401374 MPP 05/16/91 12 -- NEW BASELINE -- sup(U400722,U400727,U400751, U401041,U401075 U401227, U401293) 1774 U401356 MPP 05/16/91 3 label says volid=1772 1777 ? MPP ? ? EFIX 1779 U401382 MPP 05/31/91 4 sup(U401356) Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== X-Windows 2.1 1714 N/A Xwin 04/17/89 2 1721 N/A Xwin 1723 U400749 Xwin 07/28/89 3 coreq(U400751) (This update and ALL later X11 updates takes AIXwindows to X11R3 for AIX/RT) 1726 U400769 Xwin 09/18/90 3 coreq(U400751) U400844 1732 U400843 Xwin 12/01/89 3 coreq(U400751) U401187 1733 U400889 Xwin 01/02/90 3 coreq(U400876) 1736 U400947 Xwin 03/21/90 3 PE coreq(U400876) 1737 U401123 Xwin 07/18/90 4 PE coreq(U400991) BAD-BAD 1738 U401307 Xwin 02/14/91 4 1739 U401386 Xwin 06/12/91 ? Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== VRM 2.2 Component 560106203 1702 ? VRM ? ? EFIX 1705 ? VRM 05/11/89 2 EFIX 1706 ? VRM 08/18/89? EFIX 1707 ? VRM 08/18/89? EFIX 2707 U400754 VRM 08/08/89 2 PE coreq(U400751) BAD! wont IPL if disk errors 2710 U400828 VRM 11/07/89 2 sup(U00754) coreq(U400876) same as 1707 disks 1710 ? VRM ? 2 EFIX coreq(MPP1757) 1711 ? VRM 10/20/89 2 EFIX 1712 U401046 VRM 05/15/90 2 sup(U400754,U400828) coreq(AIX2.2.1) 1714 U401284 VRM 02/14/91 2 sup(U400828) (corrects random floating point machine checks) Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== TCP/IP Component 560106103 1707 ? TCPIP 02/09/89 1 EFIX 1713 ? TCPIP ? ? EFIX 1716 ? TCPIP ? ? EFIX 1718 ? TCPIP ? ? EFIX PE 1719 N/A TCPIP 06/??/89 ? EFIX PE 1720 ? TCPIP ? ? EFIX PE 1721 ? TCPIP ? ? EFIX 1722 ? TCPIP ? ? EFIX 1724 ? TCPIP ? ? EFIX PE (ftp is busted) 1728 ? TCPIP 10/24/89 ? EFIX PE 1730 ? TCPIP 09/21/89 2 EFIX PE 1731 ? TCPIP 10/08/89 2 EFIX 1732 1733 U401072 TCPIP 05/22/90 PE coreq(U401043,U401041) 1734 U401168 TCPIP 08/14/90 2 sup(U401072) U401195 dup(401168) 1736 U401278 TCPIP 01/18/91 2 -- NEW BASELINE -- pre(U401168) 1741 ? TCPIP ? ? EFIX PE 1742 U401385 TCPIP pre(U401278) Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== NFS V1.1 Component 560115901 1110 U400764 NFS11 09/01/89 1 1112 U400865 NFS11 12/01/89 1 sup(U400764) coreq(U400751) 1113 U400890 NFS11 01/02/90 1 sup(U400865,U400864) coreq(U400876) 1115 U400983 NFS11 04/12/90 1 sup(U400890,U400865) 1116 U401043 NFS11 05/07/90 1 sup(U400893,U400890,U400865, U400764) coreq(U401041) U401052 dup(U401043) U401104 dup(U401043) U401132 dup(U401043) U401139 dup(U401043) Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== NFS V1.2 Component 560115901 1201 U401169 NFS12 10/12/90 2 coreq(U401041,U401075) 1202 N/A NFS12 02/14/91 ? ? EFIX 1203 N/A NFS12 06/05/91 ? ? EFIX 1204 U401387 NFS12 05/31/91 2 sup(U401169) Note: even though 1204 came out BEFORE 1203, the 1204 fix disk indiates that the apars fixed on 1203 are in 1204. Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== DOS server (PCI) Component 560115701 1703 ? DOSV ? ? 1706 U401044 DOSV 05/07/90 1 sup(U400984,U400842) coreq(U400991) pre(AIX2.2.1,NEW-DOSSERV) 1709 U401383 DOSV 05/31/91 1 ============================================================================== SNA Services Component 5601061?? 1708 ? SNA ? ? 1711 ? SNA ? ? 1712 ? SNA ? ? 1713 ? SNA ? ? 1714 ? SNA ? ? 1719 U401137 SNA 07/31/90 ? PE pre(U401139) 1720 U401218 SNA ? 3 1722 U401388 SNA ? 3 Last issued update Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== Dist Serv 1.2.1 Component 560106103 1706 U400763 DS 09/01/89 ? pre(U400727,U400751) 1708 ? DS ? ? coreq(U400770) 1709 U400849 DS 12/01/89 ? sup(U400763) 1715 ? DS ? ? 2701 U400877 DS 12/27/89 ? sup(U400849,U400863) pre(U400876) U400920 doc only dup(U400877) U400952 doc only dup(U400877) U401001 doc only dup(U400877) U401001 doc only dup(U400877) U401036 doc only dup(U400877) U401039 Note: Do not confuse this 2701 distributed services disks with the 2701 updates for the base operating system. Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== Workstation Host Interface Program - V1.1 1204 U400759 WHIP11 09/01/89 1 pre(U400727) 1207 U401110 WHIP11 ? ? Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== PC Simulator 1.1.1 1210 ? PCSim ? ? 1213 U400389 PCSim 11/20/87 1 ============================================================================== Asyncronous Terminal Emulation (ATE) 1707 U401048 ATE 05/07/90 1 pre(U401041) Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== RT PC AT Coprocessor services V1.1 2206 ? COPRC ? ? ? 2207 ? COPRC ? ? ? 2209 U400??? COPRC ?/?/87 1 ? Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== Fortran 77 V1.1.1 1214 ? F77 ? ? ? 1239 ? F77 ? ? ? 1241 U401216 F77 ? 1 1245 U401390 F77 05/31/91 1 Last issued update Volid PTF# Prod Date #disk Prereq/Coreq/Notes ============================================================================== VS Fortran V1.0 F18 ? VSF ? ? F20B ? VSF ? ? F26 ? VSF ? ? F40 ? VSF 09/08/89 3 0G37 U401231 VSF ? 2 0H12 U401363 VSF 05/16/91 2 Last update issued ============================================================================== XL Fortran Note: There IS an XLFortran for the RT, but it was not widely distributed. I have been unable to determine if any updates were ever issued for the product. It was issued as a migration aid for customers to move to the AIX V3 and RS6000 systems that had been recently announced. RPQ P10095 Program Number 5799-??? ============================================================================== VS Pascal H012 U401384 VSP ? ? ? ============================================================================== VS Cobol 1.1.0 1113 U? VSC ? ? ? 1119 U401047 VSC ? ? ? ============================================================================== Personal graPHIGS V3.? Note: The update numbering scheme for graPHIGS was unlike that of ANY other RT product. I have yet to fill in this section and understand how they were issued. [Anybody a graPHIGS expert/user? - MW] ? U? ============================================================================== ------------------------------ S.9 - How to install updates to AIX. Most of the install of updates MUST be done with no users logged in to the machine, and most of the system deamons shutdown. Login as root, get any users to logoff, and issue the 'killall' command to kill all running processes and daemons. Issue the 'pdisable -a' command to disable any tty ports and psudeo terminals to prohibit more logins while the update process is in progress. WARNING: With 'cron' disabled, there is no automatic periodic 'sync' of filesystems. If possible, ensure that you issue a sync command beteeen updates and at convient intervals to help with disk and filesystem integrity. Updates are installed using the 'updatep' command. It has several arguments, the most common are: -a apply any updates on the install media. -c commit any currently installed updates. -d specifies the device or file name for updates, usually /dev/fd0 (the default). -s Display pending commit update status information -A Display a listing of all installed updates and APAR history for all products, or named product section if a argument follows the -A flag. Personally I like to install the update in one pass "updatep -a", test out the system, then later, commit the update "updatep -c". Using this procesure for installing updates has the added bonus, in that if a update fails to install, it will be automaticlly backed out, and the system restored to it's original state, rather than leaving the system in a possibly broken state with only part of the update installed. It *IS* possible for the update to be only paritially installed, especially when an out of disk space, or other catastrophic failure occurs during the update. (The worst is a power failure while install processing is in progress!) Make sure you have a good backup of any user data or any needed system files PRIOR to starting ANY system update. One thing I have done is to save a copy of the current update status before starting, and obtain one after the update, and run a diff the files. This way I can get a list of what has changed by the updates. This command is like this: updatep -A >/someplace/b4.up#### When installing updates, the update process first saves a backup copy of ALL files to be replaced and selected for install. For proper update there must be enough space in the /usr filesystem in the /usr/lpp directory tree to hold a backup copy of all updated files, and changed library routines. Some updates rebuild the kernel, and you must have at least enough free space in the root filesystem to hold at least two times the size of a standard '/unix' kernel file. Extra copies of the kernel can be found in the root filesystem named: /unix.YYDDD.nnn With "YY" the last two digits of the year, and "DDD" the julian day of the update that created this copy of the old kernel. These can be safely removed after the update that changed the kernel has been comitted. As always, the more free space in /usr and in /tmp, the safer the install will be. Using the 'updatep -a' the system will read the diskette#1 disk and will prompt you with a series of questions making sure you wish to proceed, and also to display the update disk product area and copyright information. For updates with a single product, the updatep program will now proceed to read the update media, and replace or change the necessary files. For MPP or base-OS updates, a menu will be displayed with a numbered list of product updates found on the media that are also currently installed on the system. There will be two columns listed: - No special processing needed. - Special processing required. Some updates, like X11, have several sections. These will also be displayed with a numbered list, and the last number to do all updates at once. Some base-OS product updates require a kernel rebuild. By avoiding those products first, and installing the others in groups, you can shorten the amount of time required to update a system. Updates that change the kernel, after being installed, cause the system to automaticlly shutdown and reboot, which means that you have to login again, killall, pdisable, and then when ready, comit the update. Changes or installation of these products or updates will force a kernel rebuild: - Block I/O Drivers - Ethernet Drivers - SCSI drivers - 3270 Device support - VRM device drivers Additional updates are not allowed to be installed until any prior update has been comitted. If you are useing diskettes as your update source, during the update process, follow all prompts very carefully for when to insert a different disk. Due to the structure of the update disks, if more than one section on the left side is selected, the update process will ask, and re-ask (and RE-ask) for the disks. The pattern of disks is something like this: 1 1 1,2 1,2,3 1,2,3,4 1,2,3,4,5 1,2,3,4,5,6 .. ect... Note: Some of the update disks replace the 'restore' and 'backup' commands. This is true of the 1773 update, and others. When starting the OS base opsys updates on those disks, updatep will read about to disk 11 and restore only those 2 files... *THEN* it will actually come back and re-ask for disk number 1, and then start the rest of the update of the system. Follow the prompts very carefully and there will not be a problem. DANGER: DO NOT use 'installp' with update disks, and vis versa. You can seriously damage the system. ------------------------------ S.10 - Can I install updates from other than floppies? Yes. Using the bffcreate command you can make a file of the contents of any of the update disks in a sutable format for installing directly by specifiying the resulting disk file as the install device, instead of /dev/rfd0, the default for the updatep command. To create the disk file you must have enough /tmp space to hold the entire contents of the update disk set TWICE. If your /tmp area is too small, you can point the work area for bffcreate to a different place using the -w flag. bffcreate -v -w/otherfs WARNING: The -w flag MUST have no space following the 'w' or the specified work area will be ignored. The resulting file will ONLY be placed in the following directories: - update disks: /usr/lpp.update with a file name of 'updt.yyddd.nnn' where yyddd is the Julian day and nnn is a relative number. The resulting file may then be renamed to something easy to remember, and the updatep utility can be directed to that file by: updatep -a -d/usr/lpp.update/filename - product install disks: /usr/lpp.install with a file name of 'programname.vv.rr' where programname is a partial program name and vv and rr are numbers of the version and release of the product. This file will be in the proper format for use with: installp -d/usr/lpp.install/filename NOTE: If your /usr area is too small to receive the updates you can make another filesystem named /usr/lpp.update or /usr/lpp.install and overmount it, or create soft links to other directories in a larger filesystem. The bffcreate program has no way of changing the output directory file location. ------------------------------ S.11 - Brief overview of the AIX/RT install process. * First or new installation process WARNING: The installation procedure outlined below assumes either that you do not have any software currently installed on your machine, or that you do not wish to save any of the files on your machine. If you wish to save any files or minidisks, refer to the reinstallation section. You should have in front of you the manual: "Installing and Customizing the AIX Operating System." Step 1: Planning your minidisks. Complete the minidisk worksheet as described in the manual, chapter 1. There are some excelent worksheets that will give you the approximate needed sizes of the system filesystems when including most of the optional product areas. These charts also show which filesystems that the product installation will be placing modules. Selecting the sizes of your minidisks depends on how much of the base AIX V2 system you decide to install, the size of the hard drives that you are installing to, and how much space you will desire for any of your own user areas and additional application software. The '/vrm' filesystem will need at least 3800 blocks. I recommend more if you are making any alterations of the vrm filesystem. I personally use around 5000 blocks. I, however, have been doing some VRM hacking, and this leaves me about 1000 blocks to spare. In normal use the '/vrm' space is static, so any extra will be wasted. The size of root (/) will vary a lot. Make sure that you have enough space for at least two copies of the kernel (/unix) for update handling. A working *MINIMUM* would be around 2600 to 3000 blocks free. More if you can spare it. A useful size of root will vary from 28000 to 34000 blocks, or more depending on your needs and system usage. The size of /usr will vary the most, and really depends on how much of the optional products you install. To have X11, TCP/IP and NFS will require in the range of 60000 to 150000 blocks. Space is used for temporary areas for mail (/usr/spool/mqueue) and storage of mail before being read (/usr/mail). Additional space will be needed for printing (/usr/spool/lpd and /usr/spool/qdaemon), and system temporary space (/usr/tmp). UUCP usage will also need storage space in /usr/spool/uucp. Sizing '/tmp' will depend on the amount of space you will want for editing, compiler work space, temporary mail files and work areas. A good working minimum is 5000 to 10000 blocks. User accounts by default use '/u' for home directories but can be placeed in any user filesystem, and thus will vary considerably accorting to your needs. Minimum space is 1000 blocks. Note: I have managed to install AIX V2.2.1 on two 40Mb disks, but it had no dump space, bare minimum pagespace (equal to system real memory), and a bare minimum /u, and only the base OS + TCP/IP installed. Not a very useful system. Step 2: Install VRM. Boot with the first VRM diskette and follow the instructions as described in the manual, chapters 2 and 3. I have found that this procedure works best: - Set the date and time, AND timezone *FIRST*. This will make all the rest of the installed files with the correct date, and the NVRAM clock will be proper GMT time according to your entered local time. - Choose the option 'change current choices and install'. This option will allow you to select the sizes of the VRM and initial Pagespace area. Step 3: Installing the Base System Program. Boot with the Install/Maintenance diskette and follow the instructions as described in the manual, chapter 4. The Base System Program must be installed before installing any other operating system component. I have found that this procedure works best: - Choose the option 'change current choices and install'. This option will allow you to select the sizes of all the base OS filesystems: /tmp, /usr, /, /u, and the dump space. Use the worksheet tables in step1 to help answer the filesystem size questions. - Use the menus of displayed filesystems to set the sizes of all the areas. Once a size is chosen, re-sizing it at this point is easy. After install, it is hard, so make good choices now. :-) After completing the disk sizing, the install process will proceed reading the eight disk set of base OS, and all filesystems will be sized and checked. You will also be prompted for an initial userid to be created. It will also ask if you want to have that user auto-logged in, or to run in complete multi-user mode. Step 4: Installing additional operating system programs. In addition to the Base System Program, the AIX operating system includes programs such as Extended Services, Multi-user Services and Usability Services. Use the "installp" command to install these additional programs and follow the instructions as described in the manual, chapter 5. Products you should consider installing: - Extended services sections: - Administriative support (for tar and cpio) - Extended programming support (compilers, sed and awk) - Sendmail - UUCP - if modem attached to usenet, or others. - Multi-user services sections: - System activity recording - Interworkstation commands (some scripts want the 'id' command) - GSL - for sure needed if running IBM X11 product. - VRM Device drivers sections: - Baseband adapter (if using ethernet) - SCSI adapter (if using the IBM RT SCSI adapter) - Token-Ring adapter (if using that card) - TCP/IP - if attached to a network. Required for X11. When you finished installing the additional programs, delete any leftover '/unixYYDDD.###' files using the "del" command. Step 5: Updating operating system programs. After you installed the optional programs included with AIX, you *MUST* apply the changes included on the base product Update Diskettes. Use the "updatep -ac" command and follow carefully the instructions as described in the manual, chapter 5 page 5-15. Step 6: Add any optional Licensed product to the system. After you have a running, installed system, might I suggest a backup of the system? Next, install any other products you need, such as: NFS, X11, special compiers, or other programs. Step 7: Update system to current maintence level. After much use and experience with AIX V2, I have found that the system is most useful if at least the following updates are installed, if not at the last issued update level: - 2706 For the base OS and the other base products. - 1734 For TCP/IP - 1738 For X11 AIXWindows. - 1116 For NFS 1.1 - 1204 For NFS 1.2. Note: 1773, the sucessor to 2706 is required for installing the NFS 1.2 product. Step 7: Installing applications. You have now installed the AIX operating system, and your system is ready to use. If you have additional programs to install, follow the installation procedure as described in the publications provided with these products. * Re-installation process. Save any of your tailored system configuration files, and any special files you require. The following list is some suggestions: /etc/rc.include /etc/passwd /etc/group /etc/security/* /etc/hosts /etc/filesystems /usr/adm/sendmail/* /usr/adm/uucp/* /u/* ATTENTION!! This list might NOT be complete !!! Reinstall the VRM and the AIX Base System Program. The AIX installation process destroys the /(root), /usr and /tmp minidisks. If you change any of the characteristics of the /u minidisk, it will also be destroyed. Reinstall any additional programs from the set that you had on your previous system that you desire. Enter "mdrc" (minidisk recall command) to restore your user-defined minidisks. Restore the system files that you had backed up from your previous system. Note: You must NOT directly replace /etc/filesystems from your backup. It is only for reference purposes. It would need to be merged with your newly installed /etc/filesystems if you have any NFS mounts in it. Shutdown the system and reboot with <ctl>-<alt>-<pause>. [ This section may need more work. Any other ideas/changes? - MW] ------------------------------ S.12 - Compiler usage questons? The AIX V2 system is at heart, a system V release 2 base, with BSD 4.2 and some BSD 4.3 extensions mixed in, it also has some IBM extensions and facilities by Interactive Systems, mixed in as well. The standard C compiler is mostly K&R compliant with additional compiler flags to support BSD portablity. There is *SOME* ANSI compliance in the include libraries, but it is far from complete. No ANSI prototyping is supported by the standard compiler. The compiler shipped with AIX has its own standard setup, with flags to make the include files SYSV compliant, and BSD compliant. SYSV way: cc -O -o <foo> foo.c <and other flags.> or cc -DSYSV and/or -DUSG -O -o <foo> foo.c <and other flags.> Note: The supplied header files for AIX/RT do not test for the SYSV or USG define, but a lot of public code does. X11R5 has a -DUSGISH for a merged type system like AIX/RT. BSD compatibility flags. cc -DBSD -DBSD_INCLUDES -DBSD_REMAP_SIGNAL_TO_SIGVEC \ -O -o <foo> foo.c -lbsd Note: There is another BSD flag: -DBSD_COMPILE_ONLY This flag will cause additional defines and includes that may produce a correct compile, but most likely will NOT execute correctly, due to possibly incorrect interface defines, or use AIX/RT unsupported system functions. The following discusses some of the other non-standard and special compiler flags. Programs that have large static arrays and large structures may need the '-a' flag. Using this flag will reserve an extra register for addressing, thereby reducing the optimization capabilities of the compiler. X11 programs, and other large macro heavy and/or lots of functions sources, and those with lots of external references may need one or more of these flags to increase the internal tables of the compiler: -Nn#### - symbol table, default size 1500. -Nd#### - dimension table, default size 2000. -Np#### - constant pool, default size 600. -Nt#### - parse tree, default size 1000. For programs that are heavy on floating point code may be GREATLY assisted by the following compile time flags: -f Generates code that will use either the standard Floating- Point accelerator (FPA), or the Advanced FPA. The binaries created with this flag will NOT run without at least one of the FPA's installed. Automatically includes the libfm.a math library. -f2 Generates inline code to use ONLY the Advanced Floating-Point Accelerator and Advanced processor card. Automatically includes the libfm.a math library. The inline compiler flag -Q may speed up execution time at the expense of increased module size. -Q! Automatic inlining. -Q? Show reason in output file for no inlining. -Q-name,name2 Do not inline 'name'. -Q+name,name2 Force inline of 'name'. -Q|num Limit size of function to inline, default size is 100 operations. -Q#num Limits the expansion of an individual call to num intermediate operators. Defaults to 100. -Q-@file Reads list of forbidden functions from 'file'. -Q+@file Reads list of requested functions from 'file'. Note: Requesting a function for inlining overrides the the size constraints. Rounding mode for floating-point constant folding: -yd Disables floating-point constant folding. -ym Rounds towards negative infinity. -yn Rounds to nearest whole number. This is the default action when the -y flags is specified without an argument. The specified rouding applies to constant folding in all applicable passes of the compiler. -yp Rounds towards positive infinity. -yz Rounds towards zero. -z Use the libm.a version of the following transcendental functions, instad of calls to the AIX kernel, or AFPA. acos, asin, atan, atan2, cos, exp, log, log10, sin, sqrt, tan. Programs requiring curses and/or termcap emulation need to add the -lcurses flag to their link step. Due to the work of several people the GCC compiler has finally been ported to AIX/RT. See section P.xx for porting notes for the compiler, and information on using that compiler. ================================================================================ *** FAQ Continued in software part 2 *** =============== end of ibm-rt-faq/aix-v2/software/part1 ======================== -- Posted around the first of each month to comp.sys.ibm.pc.rt, and to comp.unix.aix. This FAQ is dedicated to use of the AIX Version 2 operating system, running on the IBM RISC processor known as the RT. The RT is known also as an IBM model 6150 or 6151 machine. For AIX RT submissions E-mail to: aix-rt@antimatr.hou.tx.us For AOS RT submissions E-mail to: aos-rt@antimatr.hou.tx.us For MACH RT submissions E-mail to: mach-rt@antimatr.hou.tx.us For general Q&A submissions (hardware and other stuff) E-mail to: faq-rt@antimatr.hou.tx.us Other comments and correctons should be sent to the author: Mark Whetzel DOMAIN addr: markw@antimatr.hou.tx.us BANG address: ..!uhnix1!lobster!antimatr!markw Daytime work number 8AM-5PM M-F CST VOICE: (713) 963-2544 -- AIX..... NOT just another UNIX. (tm) Mark Whetzel | My own RT system.. My own thoughts.. DOMAIN: markw@antimatr.hou.tx.us | IBM RT/135 running AIX 2.2.1 UUCP ..!menudo!lobster!antimatr!markw | comp.sys.ibm.pc.rt FAQ maintainer.